Aerial vehicle video and telemetric data synchronization

ABSTRACT

Disclosed is a configuration to control automatic return of an aerial vehicle. The configuration stores a return location in a storage device of the aerial vehicle. The return location may correspond to a location where the aerial vehicle is to return. One or more sensors of the aerial vehicle are monitored during flight for detection of a predefined condition. When a predetermined condition is met a return path program may be loaded for execution to provide a return flight path for the aerial vehicle to automatically navigate to the return location.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/214,595, filed Dec. 10, 2018, which is a continuation of U.S.application Ser. No. 15/391,730, filed Dec. 27, 2016, now U.S. Pat. No.10,185,318, which is a continuation of U.S. application Ser. No.15/134,284, filed Apr. 20 2016, now U.S. Pat. No. 9,557,738, whichclaims the benefit of U.S. Provisional Application No. 62/302,114, filedMar. 1, 2016, U.S. Provisional Application No. 62/279,621, filed Jan.15, 2016, U.S. Provisional Application No. 62/199,356, filed Jul. 31,2015, and U.S. Provisional Application No. 62/150,703, filed Apr. 21,2015, the contents of which are incorporated by reference in theirentirety.

TECHNICAL FIELD

The disclosure generally relates to return path configurations for aremote controlled aerial vehicle.

BACKGROUND

Remote controlled devices with cameras mounted upon those devices arewell known. For example, a remote control road vehicle can be configuredto mount a camera on it to capture images as the vehicle is moved aboutremotely by a user. Similarly, remote controlled aerial vehicles, e.g.,quadcopters, have been mounted with cameras to capture aerial imagesthrough the camera as a user remotely controls the vehicle.

In some instances it may be desirable to have a remote controlled aerialvehicle return to a particular location or set down quickly. Forexample, as the aerial vehicle is in flight mechanical issues orenvironmental constraints may require that the vehicle return back to apredefined location as quickly as possible without undue delay orinterference in the return path.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed embodiments have advantages and features which will bemore readily apparent from the detailed description, the appendedclaims, and the accompanying figures (or drawings). A brief introductionof the figures is below.

FIG. 1 illustrates an example configuration of remote controlled aerialvehicle in communication with a remote controller.

FIG. 2 illustrates an example of a remote controlled aerial vehicle.

FIG. 3 illustrates an example of a remote controlled aerial vehicleelectronics and control systems.

FIG. 4 illustrates an example interconnect architecture of a remotecontrolled aerial vehicle with a gimbal.

FIG. 5 illustrates a block diagram of an example camera architecture.

FIG. 6 illustrates a block diagram of an example remote control systemof a remote controller.

FIG. 7 illustrates a functional block diagram of an example flight plancontrol system for a remote controller.

FIG. 8 illustrates a functional block diagram of an example flight plancontrol system for an remote controlled aerial vehicle.

FIG. 9 illustrates a flow diagram for an example program path operationon a remote controller.

FIG. 10 illustrates a flow diagram for an example program path operationload on a remote controlled aerial vehicle.

FIG. 11 illustrates a flow diagram for an example program path operationon a remote controlled aerial vehicle.

FIG. 12 illustrates a flow diagram for an example return path operationon a remote controlled aerial vehicle.

FIG. 13 illustrates an example user interface for a remote controller.

FIG. 14 illustrates an example machine for use with a system of theremote controlled aerial vehicle.

DETAILED DESCRIPTION

The Figures (FIGS.) and the following description relate to preferredembodiments by way of illustration only. It should be noted that fromthe following discussion, alternative embodiments of the structures andmethods disclosed herein will be readily recognized as viablealternatives that may be employed without departing from the principlesof what is claimed.

Reference will now be made in detail to several embodiments, examples ofwhich are illustrated in the accompanying figures. It is noted thatwherever practicable similar or like reference numbers may be used inthe figures and may indicate similar or like functionality. The figuresdepict embodiments of the disclosed system (or method) for purposes ofillustration only. One skilled in the art will readily recognize fromthe following description that alternative embodiments of the structuresand methods illustrated herein may be employed without departing fromthe principles described herein.

Configuration Overview

Disclosed by way of example embodiments is a remote controlled aerialvehicle with camera and mounting configuration. The remote controlledaerial vehicle includes a mounting configuration that secures a camera.The mounting configuration can be removably attachable. Moreover, thecamera can be configured so that it may be removably attachable from themounting configuration and structured to operate as a standalone mount.

Also disclosed is a configuration for a remote controlled aerial vehicleto have a flight path programmed into the remote controlled aerialvehicle and then executed during operation of the vehicle. In operation,the vehicle monitors operational, mechanical, and environmentalconfigurations to determine whether the vehicle can continue on theflight path, make adjustments or return to a predefined location. Thisconfiguration may include automating the process of flight adjustmentsand returns so that the remote controlled aerial vehicle can operatewith minimal to no impact on its immediate surroundings.

Example System Configuration

Turning now to FIG. 1, it illustrates an example configuration 100 ofremote controlled aerial vehicle in communication with a remotecontroller. The configuration 100 may include a remote controlled aerialvehicle (“aerial vehicle”) 110 and a remote controller 120. The aerialvehicle 110 and the remote controller 120 are communicatively coupledthrough a wireless link 125. The wireless link can be a WiFi link,cellular (e.g., long term evolution (LTE), 3G, 4G, 5G) or other wirelesscommunication link. The aerial vehicle 110 can be, for example, aquadcopter or other multirotor helicopter and may be referenced as a“drone”

The aerial vehicle 110 in this example includes housing 130 for payload(e.g., electronics, storage media, and/or camera), two or more arms 135,and two or more propellers 140. Each arm 135 mechanically couples with apropeller 140 to create a rotary assembly. When the rotary assembly isoperational, all the propellers 140 spin at appropriate speeds to allowthe aerial vehicle 110 lift (take off), land, hover, and move (forward,backward) in flight.

The remote controller 120 in this example includes a first control panel150 and a second control panel 155, an ignition button 160, a returnbutton 165 and a display 170. A first control panel, e.g., 150, can beused to control “up-down” direction (e.g. lift and landing) of theaerial vehicle 110. A second control panel, e.g., 155, can be used tocontrol “forward-reverse” direction of the aerial vehicle 110. Eachcontrol panel 150, 155 can be structurally configured as a joystickcontroller and/or touch pad controller. The ignition button 160 can beused to start the rotary assembly (e.g., start the propellers 140). Thereturn (or come home) button 165 can be used to override the controls ofthe remote controller 120 and transmit instructions to the aerialvehicle 110 to return to a predefined location as further describedherein. The ignition button 160 and the return button 165 can bemechanical and/or solid state press sensitive buttons. Each button maybe illuminated with one or more light emitting diodes (LED) to provideadditional details. For example the LED can switch from one visual stateto another to indicate with respect to the ignition button 160 whetherthe aerial vehicle 110 is ready to fly (e.g., lit green) or not (e.g.,lit red) or whether the aerial vehicle 110 is now in an override mode onreturn path (e.g., lit yellow) or not (e.g., lit red). It also is notedthat the remote controller 120 can include other dedicated hardwarebuttons and switches and those buttons and switches may be solid statebuttons and switches.

The remote controller 120 also may include a screen (or display) 170.The screen 170 provides for visual display. The screen 170 can be atouch sensitive screen. The screen 170 also can be, for example, aliquid crystal display (LCD), an LED display, an organic LED (OLED)display or a plasma screen. The screen 170 allow for display ofinformation related to the remote controller 120, such as menus forconfiguring the remote controller 120 or remotely configuring the aerialvehicle 110. The screen 170 also can display images captured from acamera coupled with the aerial vehicle 110. The aerial vehicle 110 andremote controller 120 are further described below.

Example Remote Controlled Aerial Vehicle

Referring now to FIG. 2, it illustrates an example of an exampleembodiment of the remote controlled aerial vehicle 110. The remotecontrolled aerial vehicle 110 in this example is shown with the housing130 and arms 135 of the arm assembly. This example embodiment shows athrust motor (which may include a rotor) 240 coupled with the end ofeach arm 130 of the arm assembly, a gimbal 210 and a camera mount 220.The thrust motor 240 couples with the propellers 140 (not shown) to spinthe propellers when the motors are operational.

The gimbal 210 may be configured to allow for rotation of an objectabout an axis. Here, the object is a camera mount 220 to which thegimbal 210 is mechanically coupled. The camera mount 210 may beconfigured to allow a camera (not shown) to couple (e.g., attach) to itand may include electrical connection points for the coupled camera. Thegimbal 210 allows for the camera mount 220 to maintain a particularposition so that the camera mounted to it can remain steady as theaerial vehicle 110 is in flight.

FIG. 3 illustrates an example embodiment of electronics and control (EC)system 310 of the aerial vehicle 110. The EC system 310 may include aflight controller 315, an electronic speed controller 320, one or morethrust motors 240, a gimbal controller 330, a telemetric subsystem 335,a power subsystem 340, a video link controller 345, a camera interface350, and a long range communication subsystem 360. The componentscommunicate directly or indirectly with each other through a data bus onthe aerial vehicle 110.

In one embodiment, the communication subsystem 360 can be a long rangeWiFi system. It also can include or be another wireless communicationsystem, for example, one based on long term evolution (LTE), 3G, 4G, or5G mobile communication standards. The communication subsystem 360 alsocould be configured with a uni-directional RC channel for communicationof controls from the remote controller 120 to the aerial vehicle 110 anda separate unidirectional channel for video downlink from the aerialvehicle 110 to the remote controller 120 (or to a video receiver wheredirect video connection may be desired). The telemetric (or sensor)subsystem 335 may include navigational components, for example, agyroscope, accelerometer, a compass, a global positioning system (GPS)and/or a barometric sensor. The power subsystem 340 can include abattery pack and a protection circuit module as well as a powercontrol/battery management system. The camera interface 350 caninterface with a camera or may include an integrated camera. Theintegrated camera may be positioned similar to the camera mount 220 andthe camera may incorporate a camera mount.

The flight controller 315 of the EC system 310 may communicate with theremote controller 120 through the communication subsystem 360. Theflight controller 315 may control the flight related operations of theaerial vehicle 110 by control over the other components such as theelectronic speed controller 320 and the telemetric subsystem 335. Theflight controller 315 may interface with the gimbal controller 330 tocontrol the gimbal 210 and the video link controller 345 for cameraoperation control.

The electronic speed controller 320 may be configured to interface withthe thrust motors 240 to control the speed and thrust applied to thepropellers 140 via the thrust motors 240 (via electronics interface) ofthe aerial vehicle 110. The video link controller 345 may be configuredto communicate with the camera interface 350 to capture and transmitimages from a camera to the remote controller 120 (or other device withscreen such as a smart phone), e.g., via the communication subsystem360. The video may be overlaid and/or augmented with other data from theaerial vehicle 110 such as the telemetric (or sensor) data from thetelemetric subsystem 335. The power subsystem 340 is configured tomanage and supply power to the components of the EC system 310.

Turning to FIG. 4, it illustrates an example interconnect architectureof the remote controlled aerial vehicle 110 with the gimbal 220. Thisexample embodiment includes the components illustrated and described inthe prior figures, e.g., FIG. 3. Also shown are components such as LEDs410 on the aerial vehicle 110 that may be used to provide vehicle statusrelated information. Also shown is a battery 440 as a part of the powersubsystem 340 and an antenna 460 as a part of the communicationsubsystem 360.

The figure illustrates in an example embodiment that the flightcontroller 315 may be coupled with two electronic speed controllers 320.Each electronic speed controller 320 in this configuration drives twothrust motors 240 (via respective electronics of each thrust motor).

Also shown is a gimbal interface 430 that may communicatively couple thegimbal controller 330 with components of the EC system 310. Inparticular, the gimbal interface 430 may be communicatively coupled withthe video link controller 345, the telemetric subsystem 335 (e.g., theGPS and the compass), and the antenna 460. The gimbal interface 430 maybe used to feed this data to the gimbal controller 330. The gimbalcontroller 330 may use this data to adjust the camera mount 220. It isnoted that the camera mount 220 can be, for example, a frame to secure acamera 450. The gimbal controller 330 may be communicative coupled withthe camera 450 through one or more camera interface 350. The camerainterface 350 can include camera communication interfaces such asuniversal serial bus (USB) or HDMI. The media captured by the camera450, e.g., still images, video, audio, can be communicated back to theaerial vehicle 110 through the camera interface 350. Data, e.g.,telemetric data from the telemetric subsystem 335, also can be sent viathe camera interface 350 to the camera 450 to associate with videocaptured and stored on the camera 450.

Example Camera Architecture

FIG. 5 illustrates a block diagram of an example camera architecture.The camera architecture 505 corresponds to an architecture for thecamera, e.g., 450. Briefly referring back to the camera 450, it caninclude a camera body, one or more a camera lenses, various indicatorson the camera body (such as LEDs, displays, and the like), various inputmechanisms (such as buttons, switches, and touch-screen mechanisms), andelectronics (e.g., imaging electronics, power electronics, metadatasensors, etc.) internal to the camera body for capturing images via theone or more lenses and/or performing other functions. In one exampleembodiment, the camera 450 may be capable of capturing spherical orsubstantially spherical content. As used herein, spherical content mayinclude still images or video having spherical or substantiallyspherical field of view. For example, in one embodiment, the camera 450may capture video having a 360 degree field of view in the horizontalplane and a 180 degree field of view in the vertical plane.Alternatively, the camera 450 may capture substantially spherical imagesor video having less than 360 degrees in the horizontal direction andless than 180 degrees in the vertical direction (e.g., within 10% of thefield of view associated with fully spherical content). In otherembodiments, the camera 450 may capture images or video having anon-spherical wide angle field of view.

As described in greater detail below, the camera 450 can include sensorsto capture metadata associated with video data, such as timing data,motion data, speed data, acceleration data, altitude data, GPS data, andthe like. In a particular embodiment, location and/or time centricmetadata (geographic location, time, speed, etc.) can be incorporatedinto a media file together with the captured content in order to trackthe location of the camera 450 over time. This metadata may be capturedby the camera 450 itself or by another device (e.g., a mobile phone orthe aerial vehicle 110 via the camera interface 430) proximate to thecamera 450. In one embodiment, the metadata may be incorporated with thecontent stream by the camera 450 as the spherical content is beingcaptured. In another embodiment, a metadata file separate from the videofile may be captured (by the same capture device or a different capturedevice) and the two separate files can be combined or otherwiseprocessed together in post-processing. It is noted that these sensorsmay be in addition to the sensors of the telemetric subsystem 335. Inembodiments in which the camera 450 is integrated with the aerialvehicle 110, the camera need not necessarily have separate individualsensors, but rather could rely upon the sensors integrated with theaerial vehicle 110.

Referring now to the details of FIG. 5, it illustrates a block diagramof the camera architecture 505 of the camera 450, according to oneexample embodiment. In the illustrated embodiment, the camera 450comprises a camera core 510 comprising a lens 512, an image sensor 514,and an image processor 516. The camera 450 may include a systemcontroller 520 (e.g., a microcontroller or microprocessor) that controlsthe operation and functionality of the camera 450. The camera 450 alsomay include a system memory 530 that is configured to store executablecomputer instructions that, when executed by the system controller 520and/or the image processors 516, may perform the camera functionalitiesdescribed herein. In some example embodiments, a camera 450 may includemultiple camera cores 510 to capture fields of view in differentdirections which may then be stitched together to form a cohesive image.For example, in an embodiment of a spherical camera system, the camera450 may include two camera cores 510 each having a hemispherical orhyper hemispherical lens that each captures a hemispherical or hyperhemispherical field of view which are stitched together inpost-processing to form a spherical image.

The lens 512 can be, for example, a wide angle lens, hemispherical, orhyper hemispherical lens that focuses light entering the lens to theimage sensor 514 which captures images and/or video frames. The imagesensor 514 may capture high-definition images having a resolution of,for example, 720p, 1080p, 4k, or higher. In one embodiment, sphericalvideo is captured as a 5760 pixels by 2880 pixels with a 360 degreehorizontal field of view and a 180 degree vertical field of view. Forvideo, the image sensor 514 may capture video at frame rates of, forexample, 30 frames per second, 60 frames per second, or higher. Theimage processor 516 performs one or more image processing functions ofthe captured images or video. For example, the image processor 516 mayperform a Bayer transformation, demosaicing, noise reduction, imagesharpening, image stabilization, rolling shutter artifact reduction,color space conversion, compression, or other in-camera processingfunctions. Processed images and video may be temporarily or persistentlystored to system memory 530 and/or to a non-volatile storage, which maybe in the form of internal storage or an external memory card.

An input/output (I/O) interface 560 transmits and receives data fromvarious external devices. For example, the I/O interface 560 mayfacilitate the receiving or transmitting video or audio informationthrough an I/O port. Examples of I/O ports or interfaces include USBports, HDMI ports, Ethernet ports, audio ports, and the like.Furthermore, embodiments of the I/O interface 560 may include wirelessports that can accommodate wireless connections. Examples of wirelessports include Bluetooth, Wireless USB, Near Field Communication (NFC),and the like. The I/O interface 560 also may include an interface tosynchronize the camera 450 with other cameras or with other externaldevices, such as a remote control, a second camera, a smartphone, aclient device, or a video server.

A control/display subsystem 570 may include various control a displaycomponents associated with operation of the camera 450 including, forexample, LED lights, a display, buttons, microphones, speakers, and thelike. The audio subsystem 550 includes, for example, one or moremicrophones and one or more audio processors to capture and processaudio data correlated with video capture. In one embodiment, the audiosubsystem 550 may include a microphone array having two or microphonesarranged to obtain directional audio signals.

Sensors 540 capture various metadata concurrently with, or separatelyfrom, video capture. For example, the sensors 540 may capturetime-stamped location information based on a global positioning system(GPS) sensor, and/or an altimeter. Other sensors 540 may be used todetect and capture orientation of the camera 450 including, for example,an orientation sensor, an accelerometer, a gyroscope, or a magnetometer.Sensor data captured from the various sensors may be processed togenerate other types of metadata. For example, sensor data from theaccelerometer may be used to generate motion metadata, comprisingvelocity and/or acceleration vectors representative of motion of thecamera 450.

Furthermore, sensor data from the aerial vehicle 110 and/or the gimbal210/gimbal controller 330 may be used to generate orientation metadatadescribing the orientation of the camera 450. Sensor data from the GPSsensor provides GPS coordinates identifying the location of the camera450, and the altimeter measures the altitude of the camera 450. In oneembodiment, the sensors 540 are rigidly coupled to the camera 450 suchthat any motion, orientation or change in location experienced by thecamera 450 is also experienced by the sensors 540. The sensors 540furthermore may associates a time stamp representing when the data wascaptured by each sensor. In one embodiment, the sensors 540automatically begin collecting sensor metadata when the camera 450begins recording a video.

Example Remote Controller System

FIG. 6 illustrates a block diagram of an example remote control system605 of a remote controller, e.g., 120. The remote control system 605includes a processing subsystem 610, a navigation subsystem 620, aninput/output (I/O) subsystem 630, a display subsystem 640, anaudio/visual (A/V) subsystem 650, a control subsystem 660, acommunication subsystem 670, and a power subsystem 680. The subsystemsare communicatively coupled through a data bus 690 and are powered,where necessary, through the power subsystem 680.

The processing subsystem 610 may be configured to provide the electronicprocessing infrastructure to execute firmware and software comprised ofinstructions. An example processing subsystem 610 is illustrated andfurther described in FIG. 14. The navigation subsystem 620 may includeelectronics, controls and interfaces for navigation instrumentation forthe remote controller 120. The navigation subsystem 620 includes, forexample, a global position system (GPS) and a compass. The GPS andcompass may be used to track location of the remote controller 120location, which can be helpful for the remote controller 120 and theaerial vehicle 110 to computationally understand location of eachrelative to the other.

The I/O subsystem 630 includes the input and output interfaces andelectronic couplings to interface with devices that allow for transferof information into or out of the remote controller 120. For example,the I/O subsystem 630 can a physical interface such as a universalserial bus (USB) or a media card (e.g., secure digital (SD)) slot. TheI/O subsystem 630 also can be associated with the communicationsubsystems 670 to include a wireless interface such as Bluetooth. It isnoted that in one example embodiment, the aerial vehicle 110 uses longrange WiFi radio within the communication subsystem 670, but also mayuse a second WiFi radio or cellular data radio (as a part of the I/Osubsystem 630) for connection other wireless data enabled devices, forexample, smart phones, tablets, laptop or desktop computers, andwireless internet access points. Moreover, the I/O subsystem 630 alsomay include other wireless interfaces, e.g., Bluetooth, forcommunicatively coupling devices that are similarly wirelessly enabledfor short range communications.

The display subsystem 640 may be configured to provide an interface,electronics, and display drivers for the screen 170 of the remotecontroller 120. The A/V subsystem 650 includes the interfaces,electronics, and drivers for an audio output (e.g., headphone jack orspeakers) as well as visual indicators (e.g., LED lighting associatedwith, for example, the buttons 160, 165).

The control subsystem 660 may include electronic and control logic andfirmware for operation with the control panels 150, 155, buttons 160,165, and other control mechanisms on the remote controller 120.

The communication subsystem 670 may include electronics, firmware andinterfaces for communications. The communications subsystem 670 caninclude one or more of wireless communication mechanisms such as WiFi(short and long range), long term evolution (LTE), 3G/4G/5G, and thelike. The communication subsystem 670 also can include wiredcommunication mechanisms such as Ethernet, USB, and HDMI.

The power subsystem 680 may include electronics, firmware and interfacesfor providing power to the system. The power subsystem 680 includesdirect current (DC) power sources (e.g., batteries), but also can beconfigured for alternating current (AC) power sources. The powersubsystem 680 also includes power management processes for extending DCpower source lifespan. It is noted that in some embodiments, the powersubsystem 680 may be comprised of power management integrated circuitand a low power microprocessor for power regulation. The microprocessorin such embodiments is configured to provide very low power states topreserve battery, and ability to wake from low power states from suchevents as a button press or an on-board sensor (like a hall sensor)trigger.

Example Flight Plan Control System for Remote Contoller

Turning now to preparing an aerial vehicle, e.g., 110 for flight, thedisclosed configuration includes mechanisms for programming the aerialvehicle 110 for flight through a remote controller, e.g., 120. Theprogram uploaded to the aerial vehicle 110 may be a flight plan. Theflight plan provides the aerial vehicle 110 with basic flight relatedparameters, even though the remote controller 120 may be used to provideoverall control over the aerial vehicle 110.

FIG. 7 illustrates a functional block diagram of an example flight plancontrol system 705 for a remote controller, e.g., 120. The system 705may include a planning module 710, a route plan database 720, a routecheck module 730, an avoidance database 740, a system check module 750and a return factors database 760. It is noted that the modules may beembodied as software (including firmware) comprised on program code (orsoftware or instructions) executable by the processing subsystem 610.

The flight plan control system 705 may be configured to provide flight(or route) planning tools that allow for preparing a flight plan of theaerial vehicle 110. The planning module 710 includes user interfacesdisplayed on the screen 170 of the remote controller 120 that allows forentering and viewing of information, such as flight path (how and wherethe aerial vehicle 110 will travel), maps (geographic information overwhere the aerial vehicle 110 will travel), environmental condition data(e.g., wind speed and direction), terrain condition data (e.g.,locations of tall dense shrubs), and other information necessary forplanning a flight of the aerial vehicle.

The route plan database 720 may provide a repository (e.g., that is partof a storage device such as an example storage device described withFIG. 14) for prepared flight plans to be stored. The route plan database720 may store plans, either previously created on the remote controller120 or uploaded into it (e.g., through the I/O subsystem 630). Thestored plans can be retrieved from the route plan database 720 andedited as appropriate through the planning module 710.

The route plan database 720 also may store preplanned (pre-programmed)maneuvers for the aerial vehicle that can be retrieved and applied witha flight plan created through the planning module 720. For example, a“loop de loop” maneuver can be pre-stored and retrieved from the routeplan database 720 and then applied to a flight plan over a mapped area(the map also can be stored in and retrieved from the route plandatabase 720) via the planning module 710. It is noted that the routeplan can be configured to provide a predefined “band” (area or regionwhere operation is permissible) within with the aerial vehicle iscontrolled through the remote controller 120.

The route check module 730 may be configured to conduct a check of thedesired flight path to evaluate potential issues with the route planned.For example, the route check module 730 may be configured to identifyparticular factors such as terrain elevation that may be challenging forthe aerial vehicle 110 to clear. The route check module 730 may checkenvironment conditions along the route planned to provide information onpotential challenges such as wind speed or direction.

The route check module 730 may also retrieve data from the avoidancedatabase 740 for use in checking a particular planned route. The datastored in the avoidance database 740 may include data such as flightrelated restriction on terms of areas/boundaries for flight (e.g., nofly areas or no fly beyond a particular boundary (aerial restrictions)),altitude restrictions (e.g., no fly above a ceiling of some predefinedaltitude or height), proximity restrictions (e.g., power lines,vehicular traffic conditions, or crowds), obstacle locations (e.g.,monuments, trees, etc.) and the like. The data retrieved from theavoidance database 740 may be used to compare against data collectedfrom the sensors on the aerial vehicle 110 to see whether the collecteddata corresponds with, for example, a predefined condition, whether thecollected data is within a predetermined range of parameters that iswithin an acceptable range of error, etc.

The route check module 730 also may include information corresponding toinformation on where the aerial vehicle 110 can or cannot set down. Forexample, the route check module 730 may incorporate in information wherethe aerial vehicle 110 cannot land (“no land zone”), for example,highways, bodies of water (e.g., pond, stream, rivers, lakes, ocean,etc.) or restricted areas. Some retrieved restrictions may be used toadjust the planned route before flight so that when the plan is uploadedinto the aerial vehicle flight along a particular path is not allowed interms of remote controller 120 control with flying in that path. Otherretrieved restriction data from the avoidance database 740 can be storedwith the route plan and also may be uploaded into the aerial vehicle 110for use during the flight by the aerial vehicle 110. The storedinformation can be used to make route adjustments when detected, e.g.,via the system check module 750 described below.

Referring back to the route check module 730, it also can be configuredto alter or provide recommendations to alter the route plan to removeconditions in the flight plan path that may not be conducive for theaerial vehicle 110 to fly through. The altered or suggested path can bedisplayed through the planning module 710 on the screen 170 of theremote controller 120. The revised route can be further modified if sodesired and checked again by the route check module 730 in an iterativeprocess until the route is shown as clear for flight of the aerialvehicle 110.

The system check module 750 may be configured to communicate with theaerial vehicle, e.g., through the communication subsystem 670. Thesystem check module 750 receives data from the aerial vehicle 110corresponding to conditions corresponding to the aerial vehicle 110 orthe surroundings within which the aerial vehicle 110 is operating. Thesystem check module 750 can interface with the planning module 710 androute check module 730 to make route adjustments for the aerial vehicle110 as it operates and moves along the planned route.

The planning module 710, and in some embodiments the route check module730, also interface with the return factors database 760. The returnfactors database 760 stores return related data corresponding to whenthe aerial vehicle 110 should return to a predefined spot. This data canbe stored with the route plan and uploaded into the aerial vehicle 110.The data also can be used by the system check module 750 to trigger anaction for the aerial vehicle 110 to go to the return location. Thereturn data can be data such as aerial vehicle 110 related data such asbattery power (e.g., return if battery power below predefined thresholdthat would prevent return of the aerial vehicle 110) or mechanicalcondition (e.g., motor engine stall or burnout). The return data alsocan be environment data (e.g., wind speed in excess of a predefinedthreshold) or terrain data (e.g., tree density beyond predefinedthreshold). The return location can be predefined through the planningmodule 710 by providing, for example, GPS coordinate. Alternately, itcan be the location of the remote controller 120. The aerial vehicle 110may be configured to set down at or near its current location if thesystem check module 750 determines that the aerial vehicle 110 will notbe able to return to the predefined location in view of the return datainformation received.

It is noted that the databases 720, 740, 760 of the system 705 may beupdated and/or augmented. For example, where there may be a local WiFior cellular data connection, e.g., through the I/O subsystem 630, thedata gathered from sources such as the internet can be used to updatethe route plan database 720, the avoidance database 740, and the returnfactors database 760. Moreover, with such data communication, thedatabases can be updated in real-time so that information may be updatedand utilized during flight. Further, the updated data can be transmittedto the communication subsystem 360 of the aerial vehicle 110 in realtime to update route or return path information (further describedbelow) as it becomes available.

Additional examples of route plan related configurations on a remotecontroller 120 are described with FIGS. 9 and 10. FIG. 9 illustrates aflow diagram for an example route plan programmed on a remote controller120. The process starts 910 with the remote control system 605determining 915 whether there is pre-defined flight route (or path). Ifnot, the process receives flight route details 920 using, for example,the planning module 710 and route planning database 720. The processanalyzes 925 route restrictions using, for example, the route checkmodule 730 and avoidance database 740. The process also analyzes 930system constraints through, for example, the avoidance database andsystem check module 750 (e.g., battery life left on aerial vehicle 110).The process uploads 935 the route details to the aerial vehicle 110. Theroute also may be stored the route plan database 720 before being readyfor next actions 945.

If the process determines 915 that a predefined route will be used, thatroute plan can be retrieved from the route plan database 720. Theretrieved route plan is uploaded 935 to the aerial vehicle 935. Ifadjustments are made to the retrieved route plan, the process mayundertake the steps of analyzing 925 the route restrictions andanalyzing the system constraints 930 before being uploaded to the aerialvehicle 935. The processes of analyzing 925, 930 may be iterative beforeupload and before being ready 945 for the next actions.

Turning to FIG. 10, it illustrates a flow diagram for an example programload operation onto the aerial vehicle 110. The process starts 1010 withthe flight controller 315 processing subsystem receiving 1015 the routeinformation from the remote controller 120. The received routeinformation is stored 1020 in a storage (e.g., memory and/or flashstorage). When ready for execution, the process retrieves the storedroute information and loads 1025 the route information and correspondingexecutable code for execution by the flight controller 315 processingsubsystem. The aerial vehicle 110 is ready 1030 for flight using theloaded route information.

Example Flight Control System for Aerial Vehicle

Turning now to FIG. 8, it illustrates a functional block diagram of anexample flight control system 805 for a remote controlled aerialvehicle, e.g., 110. The flight control system 805 may include a routeplan module 810, a systems check module 820, a control module 830,tracking module 840, a local route database 850 and a tracking database860. It is noted that the modules of the flight control system 805 maybe embodied as software (including firmware) comprised on program code(or software or instructions) stored in a storage medium and executableby the flight controller 315 processing subsystem.

The route plan module 810 may be configured to execute the route for theaerial vehicle 110. The route plan may be one uploaded from the remotecontroller 120 as described with FIG. 10. The route plan may betransmitted via the communication subsystem 670 of the remote controller120 and received by the communication subsystem 360 of the aerialvehicle 110. The route plan can be configured to provide a predefined“band” within with the aerial vehicle is controlled. The systems checkmodule 820 may be configured to monitor operational systems of theaerial vehicle 110 and flight environment and terrain sensor datacaptured by the aerial vehicle 110 when in operation. The operationalsystems information may include information related to flight of theaerial vehicle 110, for example, remaining battery power, mechanicaloperation, and electrical operation. Flight environment and terrainsensor data corresponds to data from the telemetric subsystem 335 of theaerial vehicle 110, for example, temperature, moisture, wind direction,object detection as well as altitude and direction (e.g., heading) data.

The control module 830 may be configured to control operation of theaerial vehicle 110 when it is in flight. The control module 830 may beconfigured to receive control commands from the remote controller 120.The received commands may be, for example, generated via the controlpanels 150, 155 and transmitted from the communication subsystem 670 ofthe remote controller 120 for receiving and processing at the aerialvehicle 110 via its communication subsystem 360 and flight controller315. The received commands may be used by the control module 830 tomanipulate the appropriate electrical and mechanical subsystems of theaerial vehicle 110 to carry out the control desired.

The control module 830 also may interface with the route plan module 810and the systems check module 820 to ensure that the controls executedare within the permissible parameter of the route (or path) provided bythe route plan module 810. Further, when an aerial vehicle 110 is inflight, there may be instances in which early detection of potentialproblems may be beneficial so that course (including flight)modifications can be taken when necessary and feasible. The controlmodule 830 also may make course changes in view of receiving informationfrom the systems check module 820 that may indicate that such coursecorrection is necessary, for example, to navigate around an objectdetected by the telemetric subsystem 335 or picked up and analyzed fromthe camera 450. Other example course changes may occur due to windlevels exceeding a threshold at a particular altitude so that the aerialvehicle may move to a lower altitude where wind may be less of an issuedespite the control information received from the remote controller 120.In making these changes, the control module 830 may work with thetracking module 860 to update the local route database 850 to identifylocation of objects or identify areas of flight that would be identifiedfor avoidance for other reasons (e.g., whether conditions, electronicinterference, etc.) for tracking by the tracking module 840 and forlater download to an avoidance database, e.g., 740.

The tracking module 840 may be configured to track the flight of theaerial vehicle 840 (e.g., data corresponding to “clear” path of flying).The tracking module 840 also may store this information in the trackdatabase 860 and may store information in the local route database 850.The tracking module 840 may be used to retrieve the route the aerialvehicle 110 actually took and use that data to track back to aparticular location. This may be of particular interest in situations inwhich the aerial vehicle 110 needs to be set down (e.g., land) as quickas possible and/or execute a return path. For example, if the systemscheck module 820 detects an impending power, electrical or mechanicalissue that may affect further flying of the aerial vehicle 110, it mayinstruct the control module 830 to configure itself into an overridemode. In the override mode, the control module 830 now limits or cutsoff the control information received from the remote controller 120. Thecontrol module 830 checks with the tracking module 840 on a return pathfor the aerial vehicle 110 to identify a location where the aerialvehicle 110 can be set down as quickly as possible based on data fromthe systems control module 820, e.g., amount of battery power remainingand/or execute a return path. For example, upon executing a return path,the control module 830 may determine that the battery power left may notallow for return to a predefined location and may instead need to landsomewhere along the clear path.

FIG. 11 provides an example of additional details for flight controloperation on the aerial vehicle 110. In particular, FIG. 11 illustratesa flow diagram for an example operation on the aerial vehicle 110. Theprocess starts 1110 with control information being received from theremote controller 120 through the communication subsystem 360 of theaerial vehicle 110. The control information is processed by the flightcontroller 315 to control 1115 the mechanical and electrical componentsof the aerial vehicle within the context of the programmed flight route.The telemetric subsystem 335 receives 1120 flight data information fromsensors on board the aerial vehicle 315. This data is analyzed 1125 bythe systems check module 820. The control module 830 may augment 1130the analyzed data based on other information to modify the route, e.g.,detection of an object by the telemetric subsystem 335 or image analysisof an image captured by the camera 450. In such instances the aerialvehicle 110 flight controls may be adjusted 1135 by the control module830. When the flight path is completed 1140, the aerial vehicle maycontinue to fly within the parameters of system operation and flightroute (or path) until the aerial vehicle is landed 1145. It is notedthat the aerial vehicle 110 will not land within locations predefined as“no land zones.” In such situations, a user of the remote controller 120will continue to fly the aerial vehicle 110 to an area where landing1145 is permitted.

Example Return Path Operation on Aerial Vehicle

As noted previously, there may be instances in which the aerial vehicle110 may need to execute a return path. For example, operationalconditions on the aerial vehicle 110 or a signal of return to home fromthe remote controller 120 may trigger a return path. On the aerialvehicle 110, the route plan module 810, control module 830 and/ortracking module 840 may be configured to provide a return path. Thereturn path may have been preprogrammed from the flight plan, butthereafter modified with information picked up during flight of theaerial vehicle 110 and stored during flight. For example, during flight,the sensors on the aerial vehicle 110 may detect obstacles that shouldbe avoided, but were in the pre-programmed return path. The detectedobstacles and/or corresponding location data (e.g., GPS coordinates orpoints) of that obstacle is stored in the local route database 850. Whenthe route plan module 810, control module 830 and/or tracking module 840execute the return path operation on the aerial vehicle 110, the returnpath program is retrieved, data is extracted corresponding to obstacles(or other avoidance data) determined to be in the return path that weredetected and stored during flight, the return path program is revised toadjust for those obstacles (e.g., changes flight path to clear object),and the modified return path is executed so that the obstacles areavoided on the return path.

The disclosed configuration beneficially implements an intelligentreturn to home behavior for the aerial vehicle 110. The return to homeconfiguration may use a return path that is a direct from a currentlocation to a predefined location. Alternately, or in addition, thedirect route may incorporate in obstacle avoidance. By way of example,assume during flight the aerial vehicle 110 flies around a tree. Thisdata, for example, location data, for the fly around may be stored inthe aerial vehicle 110. Later, if a “return to home” (or “come home”)button is selected on the remote controller 120, the aerial vehicle 110return path tracks back along the direct route, but avoids flyingdirectly into a tree, which is identified as an obstacle. Hence, thedisclosed configuration return path can track back along what may be aclear path on the way back because such path avoided obstacles. Inaddition, the clear path may be direct path from a current location to apredetermined location (e.g., an initial take off location and/orinitial location where data was captured) and may avoid redundant pointsalong the route (e.g., multiple passes around a tree or building). Theclear path may be saved within the aerial vehicle. In some exampleembodiments, in addition to obstacle avoidance, the return path programmay use a direct route back to the predefined location to land or aplace to land along that route that is determined to be clear. Landingat a place other than the predefined location may be due to otherfactors coming into consideration, for example, if battery power isinsufficient to return to predefined location or mechanical integritywould prevent return to predefined location.

The disclosed configuration may reduce or remove aspects of flightbehavior of the aerial vehicle that would be unnecessary for a returnpath. For example if the aerial vehicle 110 flew several loops around atree, it may be undesirable to backtrack all of the loops when on areturn path. Accordingly, the aerial vehicle 110 is configured to markareas as “clear” (i.e., areas that are clear can then be identifiedthrough “clear breadcrumbs”) as the aerial vehicle 110 is in flight. Theclear path may be generated, for example, by removing location data(e.g., GPS) of the tracked flight path that may be redundant and/oraccounting for obstacle data that may have been collected so as to avoidthose obstacles. Further, it may be a direct flight path from a currentlocation of the aerial vehicle to a predetermined location (e.g.,initial take off location). The data corresponding to “clear” can beassembled into a graph for use in a return path. Thereafter, if theaerial vehicle 110 needs to come back (e.g., execute a return path) tothe starting location the aerial vehicle 110 can take the shortest paththrough the graph of the cleared areas. This information can be storedand used through the control module 830 and/or the tracking module 840.Hence, if the aerial vehicle 110 flew several loops and figure eightsand they intersect, the control module 840 can make connections at thosepoints, build a graph corresponding to the points in that flight, andtake a shortest path through cleared area back to a return point, forexample, by removing redundant location data collected along the flightpath. The process also may use an initial take off location of theaerial vehicle (e.g., where the aerial vehicle started flying from) asthe return location.

FIG. 12 illustrates a flow diagram for an example return path operationon a remote controlled aerial vehicle 110. The return path may beexecuted due to voluntary action, e.g., user selection of the returnbutton 165 on the remote controller 120, or through involuntary action.Involuntary actions may include system related issue on the aerialvehicle 110, for example, low battery power or mechanical or electricalissues. The involuntary actions also may be triggered from sources suchas location information or environmental information such as flyingbeing a defined boundary or area, climatic issues (wind) or physicalconsiderations such as object density. The aerial vehicle monitoring maybe set up through the return factors database 760 and monitored fortriggering of a return condition through the system check module 820,which can work in conjunction with the control module 830 to trigger areturn mode.

In this example, process starts 1210 by detection 1215 of a returncondition, for example, the systems check module 820. The control module830, in conjunction with the route plan module 810 triggers areprogramming 1220 of the aerial vehicle to now follow a return path.The control module 830 may work in conjunction with the route planmodule 810, which may have preprogrammed coordinates of a returnlocation, and/or the tracking module 840, which includes information onpossible return path accounting for potential obstacles as may have beenlogged in the track database 860 during flight of the aerial vehicle110. It is noted that in some embodiments the aerial vehicle 110 alsomay track “clear” areas during flight and store those locations.Thereafter if a return path is triggered, either manually orautomatically, the “cleared” location data points are retrieved togenerate a return flight path that the control module 830 can execute.This configuration may be beneficial, for example, if no return path isprogrammed or circumstances do not allow for return to precise “home”location.

As the return flight path is executed and the aerial vehicle 110 can bechanged to operate in a return to home mode. The control module 830 mayoverride control information arriving from the remote controller 120 andengage in an auto-pilot to navigate to the location pre-defined with thereturn to home. If there are flight adjustments 1225, the process mayalter the flight path according to information stored and processed bythe tracking module 840 and the track database 860 and local routedatabase 850. The control module 830 may be configured to control 1240the aerial vehicle back to the return location 1250. The return location1250 may be identified in the route plan module 810 (original route planmay include coordinates for return location), or may use the location ofthe remote controller 120 (using its GPS location as a tracked beacon),or may identify an intermediate point as determined through the localroute database 850 and/or the track database 860 in conjunction with thetracking module 840 and the route plan module 810.

It is noted that other operational scenarios also may trigger a returnflight path. For example, the systems check module 820 may closelymonitor maintenance of a communication link between the communicationssubsystem 360 of the aerial vehicle 110 and the communication subsystem670 of the remote controller 120. A loss of a communication link betweenthe communications subsystem 360 of the aerial vehicle 110 and thecommunication subsystem 670 of the remote controller 120 may beindicative of a need to trigger a return path. In this example, thesystem can be configured so that if communication link has been severed,the systems check module 820 notifies the control module 830 to try toreestablish the communication link. If the communication link is notestablished within a predefined number of tries or a predefined timeperiod, the control module 830 will trigger the start of the return pathas described above.

Remote Controller User Interface Example

FIG. 13 illustrates an example user interface 1305 for use with theremote controller 120. The user interface 1305 is configured for displayon the screen 170 of the remote controller 120. In this example, theuser interface 1305 corresponds to a “dashboard” for the aerial vehicle110. In one embodiment, the remote controller 120 may receive, e.g., viathe I/O subsystem 630 and/or communications subsystem 670, sensor datalogged by the telemetric subsystem 335 (and transmitted via thecommunication subsystem 360) of the aerial vehicle 110 as it is inflight. In one example embodiment, the aerial vehicle 110 canincorporate the telemetric (or sensor) data with video that istransmitted back to the remote controller 120 in real time. The receivedtelemetric data is extracted from the video data stream and incorporateinto predefine templates for display with the video on the screen 170 ofthe remote controller 120. The telemetric data also may be transmittedseparate from the video from the aerial vehicle 110 to the remotecontroller 120. Synchronization methods such as time and/or locationinformation can be used to synchronize the telemetric data with thevideo at the remote controller 120. This example configuration allows auser, e.g., operator, of the remote controller 120 to see where theaerial vehicle 110 is flying along with corresponding telemetric dataassociated with the aerial vehicle 110 at that point in the flight.Further, if the user is not interested in telemetric data beingdisplayed real-time, the data can still be received and later appliedfor playback with the templates applied to the video.

The predefine templates can correspond with “gauges” that provide avisual representation of speed, altitude, and charts, e.g., as aspeedometer, altitude chart, and a terrain map. The populated templates,which may appear as gauges on screen 170 of the remote controller 120,can further be shared, e.g., via social media, and or saved for laterretrieval and use. For example, a user may share a gauge with anotheruser by selecting a gauge (or a set of gauges) for export. Export can beinitiated by clicking the appropriate export button, or a drag and dropof the gauge(s). A file with a predefined extension will be created atthe desired location. The gauge to be selected and be structured with aruntime version of the gauge or can play the gauge back through softwarethat can read the file extension.

Example Machine Architecture

As has been noted, the remote controlled aerial vehicle 110 can beremotely controlled from the remote controller 120. The aerial vehicle110 and the remote controller 120 are machines that that be configuredoperated using software. FIG. 13 is a block diagram illustratingcomponents of an example machine able to read instructions from amachine-readable medium and execute them in one or more processors (orcontrollers). All or portions of the example machine described in FIG.14 can be used with the aerial vehicle 110 or the remote controller 120and/or other parts of a system that interfaces with the aerial vehicle110 and/or remote controller 120.

In FIG. 14 there is a diagrammatic representation of a machine in theexample form of a computer system 1400. The computer system 1400 can beused to execute instructions 1424 (e.g., program code or software) forcausing the machine to perform any one or more of the methodologies (orprocesses) described herein. In alternative embodiments, the machineoperates as a standalone device or a connected (e.g., networked) devicethat connects to other machines. In a networked deployment, the machinemay operate in the capacity of a server machine or a client machine in aserver-client network environment, or as a peer machine in apeer-to-peer (or distributed) network environment.

The machine in this example is a handheld controller to control theremote controlled aerial vehicle, e.g., 110. However, the architecturedescribed may be applicable to other computer systems that operate inthe system of the remote controlled aerial vehicle, e.g., 110, withcamera, e.g., 450, and mounting configuration, e.g., in setting up alocal positioning system. These other example computer systems include aserver computer, a client computer, a personal computer (PC), a tabletPC, a smartphone, an internet of things (IoT) appliance, a networkrouter, switch or bridge, or any machine capable of executinginstructions 1424 (sequential or otherwise) that specify actions to betaken by that machine. Further, while only a single machine isillustrated, the term “machine” shall also be taken to include anycollection of machines that individually or jointly execute instructions1424 to perform any one or more of the methodologies discussed herein.

The example computer system 1400 includes one or more processing units(generally processor 1402). The processor 1402 is, for example, acentral processing unit (CPU), a graphics processing unit (GPU), adigital signal processor (DSP), a controller, a state machine, one ormore application specific integrated circuits (ASICs), one or moreradio-frequency integrated circuits (RFICs), or any combination ofthese. The computer system 1400 also includes a main memory 1404. Thecomputer system may include a storage unit 1416. The processor 102,memory 1404 and the storage unit 1416 communicate via a bus 1408.

The computer system 1406 may include a static memory 1406, a screendriver 1410 (e.g., to drive a screen, e.g., 170, such as plasma displaypanel (PDP), a liquid crystal display (LCD), or a projector). Thecomputer system 1400 may also include input/output devices, e.g., analphanumeric input device 1412 (e.g., a keyboard), a dimensional (e.g.,2-D or 3-D) control device 1414 (e.g., a mouse, a trackball, a joystick,a motion sensor, or other pointing instrument), a signal generationdevice 1418 (e.g., a speaker), and a network interface device 1420,which also are configured to communicate via the bus 1408.

The storage unit 1416 includes a machine-readable medium 1422 on whichis stored instructions 1424 (e.g., software) embodying any one or moreof the methodologies or functions described herein. The instructions1424 may also reside, completely or at least partially, within the mainmemory 1404 or within the processor 1402 (e.g., within a processor'scache memory) during execution thereof by the computer system 1400, themain memory 1404 and the processor 1402 also constitutingmachine-readable media. The instructions 1424 may be transmitted orreceived over a network 1426 via the network interface device 1420.

While machine-readable medium 1422 is shown in an example embodiment tobe a single medium, the term “machine-readable medium” should be takento include a single medium or multiple media (e.g., a centralized ordistributed database, or associated caches and servers) able to storethe instructions 1424. The term “machine-readable medium” shall also betaken to include any medium that is capable of storing instructions 1424for execution by the machine and that cause the machine to perform anyone or more of the methodologies disclosed herein. The term“machine-readable medium” includes, but not be limited to, datarepositories in the form of solid-state memories, optical media, andmagnetic media.

Additional Considerations

The disclosed configuration beneficially executes detects conditions inan aerial vehicle that automatically triggers a return path for havingthe aerial vehicle return or set down in a predefined location.Moreover, the disclosed configurations also can apply to other vehiclesto automatically detect and trigger a return path

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms, for example, as illustrated anddescribed within FIGS. 3-13. Modules may constitute either softwaremodules (e.g., code embodied on a machine-readable medium or in atransmission signal) or hardware modules. A hardware module is tangibleunit capable of performing certain operations and may be configured orarranged in a certain manner. In example embodiments, one or morecomputer systems (e.g., a standalone, client or server computer system)or one or more hardware modules of a computer system (e.g., a processoror a group of processors) may be configured by software (e.g., anapplication or application portion) as a hardware module that operatesto perform certain operations as described herein.

In various embodiments, a hardware module may be implementedmechanically or electronically. For example, a hardware module maycomprise dedicated circuitry or logic that is permanently configured(e.g., as a special-purpose processor, such as a field programmable gatearray (FPGA) or an application-specific integrated circuit (ASIC)) toperform certain operations. A hardware module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

The various operations of example methods described herein may beperformed, at least partially, by one or more processors, e.g.,processor 1402, that are temporarily configured (e.g., by software) orpermanently configured to perform the relevant operations. Whethertemporarily or permanently configured, such processors may constituteprocessor-implemented modules that operate to perform one or moreoperations or functions. The modules referred to herein may, in someexample embodiments, comprise processor-implemented modules.

The one or more processors may also operate to support performance ofthe relevant operations in a “cloud computing” environment or as a“software as a service” (SaaS). For example, at least some of theoperations may be performed by a group of computers (as examples ofmachines including processors), these operations being accessible via anetwork (e.g., the Internet) and via one or more appropriate interfaces(e.g., application program interfaces (APIs).)

The performance of certain of the operations may be distributed amongthe one or more processors, not only residing within a single machine,but deployed across a number of machines. In some example embodiments,the one or more processors or processor-implemented modules may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleembodiments, the one or more processors or processor-implemented modulesmay be distributed across a number of geographic locations.

Some portions of this specification are presented in terms of algorithmsor symbolic representations of operations on data stored as bits orbinary digital signals within a machine memory (e.g., a computermemory). These algorithms or symbolic representations are examples oftechniques used by those of ordinary skill in the data processing artsto convey the substance of their work to others skilled in the art. Asused herein, an “algorithm” is a self-consistent sequence of operationsor similar processing leading to a desired result. In this context,algorithms and operations involve physical manipulation of physicalquantities. Typically, but not necessarily, such quantities may take theform of electrical, magnetic, or optical signals capable of beingstored, accessed, transferred, combined, compared, or otherwisemanipulated by a machine. It is convenient at times, principally forreasons of common usage, to refer to such signals using words such as“data,” “content,” “bits,” “values,” “elements,” “symbols,”“characters,” “terms,” “numbers,” “numerals,” or the like. These words,however, are merely convenient labels and are to be associated withappropriate physical quantities.

Unless specifically stated otherwise, discussions herein using wordssuch as “processing,” “computing,” “calculating,” “determining,”“presenting,” “displaying,” or the like may refer to actions orprocesses of a machine (e.g., a computer) that manipulates or transformsdata represented as physical (e.g., electronic, magnetic, or optical)quantities within one or more memories (e.g., volatile memory,non-volatile memory, or a combination thereof), registers, or othermachine components that receive, store, transmit, or displayinformation.

As used herein any reference to “one embodiment” or “an embodiment”means that a particular element, feature, structure, or characteristicdescribed in connection with the embodiment is included in at least oneembodiment. The appearances of the phrase “in one embodiment” in variousplaces in the specification are not necessarily all referring to thesame embodiment.

Some embodiments may be described using the expression “coupled” and“connected” along with their derivatives. For example, some embodimentsmay be described using the term “coupled” to indicate that two or moreelements are in direct physical or electrical contact. The term“coupled,” however, may also mean that two or more elements are not indirect contact with each other, but yet still co-operate or interactwith each other. The embodiments are not limited in this context.

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a process,method, article, or apparatus that comprises a list of elements is notnecessarily limited to only those elements but may include otherelements not expressly listed or inherent to such process, method,article, or apparatus. Further, unless expressly stated to the contrary,“or” refers to an inclusive or and not to an exclusive or. For example,a condition A or B is satisfied by any one of the following: A is true(or present) and B is false (or not present), A is false (or notpresent) and B is true (or present), and both A and B are true (orpresent).

Use of the “a” or “an” may be employed to describe elements andcomponents of the embodiments herein. This is done merely forconvenience and to give a general sense of the invention. Thisdescription should be read to include one or at least one and thesingular also includes the plural unless it is obvious that it is meantotherwise.

Upon reading this disclosure, those of skill in the art will appreciatestill additional alternative structural and functional designs for asystem and a process for automatically detecting and executing a returnpath for a vehicle through the disclosed principles herein. Thus, whileparticular embodiments and applications have been illustrated anddescribed, it is to be understood that the disclosed embodiments are notlimited to the precise construction and components disclosed herein.Various modifications, changes and variations, which will be apparent tothose skilled in the art, may be made in the arrangement, operation anddetails of the method and apparatus disclosed herein without departingfrom the spirit and scope defined in the appended claims.

1-20. (canceled)
 21. A method, comprising: receiving a video captured by a camera of an aerial vehicle; synchronizing telemetric data and the video to generate synchronized data; and displaying, via a user interface corresponding to the aerial vehicle and as selectable options, the synchronized data and one or more applications associated with the aerial vehicle.
 22. The method of claim 21, wherein the user interface is displayed by any of a remote controller or a smartphone in communication with the aerial vehicle.
 23. The method of claim 21, wherein the video is captured by the camera while the aerial vehicle is executing a flight path.
 24. The method of claim 23, wherein at least a portion of the video corresponds to an avoidance of one or more obstacles detected by the aerial vehicle along the flight path.
 25. The method of claim 24, wherein the flight path is a modified flight path.
 26. The method of claim 25, wherein the modified flight path is generated by the aerial vehicle based on each location of the one or more obstacles and based on one or more redundant routes that trace around the one or more obstacles.
 27. The method of claim 21, wherein the user interface is configured based on a predefined template that includes the selectable options.
 28. The method of claim 21, wherein the one or more applications include one or more gauges.
 29. The method of claim 21, further comprising: receiving an indication that one or more sensors of the aerial vehicle has detected a predefined condition.
 30. The method of claim 29, wherein the predefined condition includes any of a structural condition of a mechanical component of the aerial vehicle and an operational condition of an electronic component of the aerial vehicle.
 31. A system, comprising: a processor; and a memory including instructions that, when executed by the processor, cause the processor to: synchronize telemetric data and video captured by an aerial vehicle to generate synchronized data; and display, via a user interface corresponding to the aerial vehicle and as selectable options, the synchronized data and one or more applications associated with the aerial vehicle.
 32. The system of claim 31, wherein the user interface is displayed by any of a remote controller or a smartphone in communication with the aerial vehicle.
 33. The system of claim 31, wherein the video is captured by the aerial vehicle while the aerial vehicle is executing a flight path.
 34. The system of claim 33, wherein at least a portion of the video corresponds to an avoidance of one or more obstacles detected by the aerial vehicle along the flight path.
 35. The system of claim 31, wherein the user interface is configured based on a predefined template that includes the selectable options.
 36. The system of claim 31, further including instructions that, when executed by the processor, cause the processor to: receive an indication that one or more sensors of the aerial vehicle has detected a predefined condition, the predefined condition including any of a structural condition of a mechanical component of the aerial vehicle and an operational condition of an electronic component of the aerial vehicle.
 37. A non-transitory computer readable storage medium comprising instructions that, when executed by a processor, cause the processor to: synchronize data and video captured by an aerial vehicle to generate synchronized data; and display, via a user interface and as selectable options, the synchronized data and one or more applications associated with the aerial vehicle.
 38. The non-transitory computer readable storage medium of claim 37, wherein the data is telemetric data.
 39. The non-transitory computer readable storage medium of claim 37, wherein the user interface is configured based on a predefined template that includes the selectable options.
 40. The non-transitory computer readable storage medium of claim 37, further including instructions that, when executed by the processor, cause the processor to: receive an indication that one or more sensors of the aerial vehicle has detected any of a structural condition of a mechanical component of the aerial vehicle and an operational condition of an electronic component of the aerial vehicle. 